Package-level declarations
Types
Runs the mark-and-sweep collector for a context: selects ACTIVE propositions, hands them to one or more CollectorStrategys for marking, then asks the SweepPolicy what to do with each marked one.
Immutable summary of a single collector run.
The "mark" half of the mark-and-sweep collector: looks at candidate propositions and reports which ones should be collected, and why.
Result of memory consolidation.
A CollectorStrategy that marks propositions whose decayed confidence has fallen below a staleness threshold.
Default CollectorRunner implementation.
Default DreamLoopOrchestrator: runs a list of ConsolidationPasses as a single cycle.
Default implementation of MemoryConsolidator.
Default MemoryMaintenanceOrchestrator: runs consolidation, abstraction, retirement, and optionally the mark-and-sweep collector as a four-stage pipeline.
Default implementation of MemoryRetriever backed by a PropositionRepository.
Composes ConsolidationPasses into a repeatable consolidation cycle — the "dream loop".
Summary of a single dream-loop consolidation cycle.
A CollectorStrategy that finds near-duplicate propositions and marks all but the strongest member of each duplicate group.
Strategy interface for classifying propositions into knowledge types. Implementations can use different heuristics based on domain needs.
Result of a memory maintenance run.
Consolidates session propositions into long-term memory. End-of-session process that decides what to keep, reinforce, or discard.
Orchestrates memory maintenance — consolidating, abstracting, retiring, and persisting — as a single entry point suitable for end-of-session or scheduled batch runs.
Propositions organized by knowledge type.
Projects propositions into memory organized by knowledge type.
Retrieves propositions with memory semantics. Combines multiple retrieval strategies: similarity, entity overlap, recency.
Represents a merge of multiple propositions into one.
A CollectorStrategy that also wants the full CollectorRunContext (run id, dry-run flag, clock), not just the bare context id — so it can tag whatever it writes (e.g. trace rows) with the run that produced them.